Skip to content

[SOP Workgroup] Article 1 - Station Regulations - #108

Draft
funkycmm wants to merge 52 commits into
funky-station:mainfrom
Joaco545:A1-INDI-PR
Draft

[SOP Workgroup] Article 1 - Station Regulations#108
funkycmm wants to merge 52 commits into
funky-station:mainfrom
Joaco545:A1-INDI-PR

Conversation

@funkycmm

@funkycmm funkycmm commented Jun 5, 2026

Copy link
Copy Markdown

This is a separated PR from the SOP Workgroup containing the design document and contents of Article 1 of the NCLR.

Joaco545 and others added 30 commits April 26, 2026 00:28
Filled out the Title section
Created a basic skeleton for the Features to be added section
Set the technical considerations section to mention it's just yaml
Copied the template, one for each article
Added the Article files for each article
Initial writeup for regulations.
Kinda need Githubs MD viewer to adjust now
Initial update from Google Docs
@ferynn

ferynn commented Jul 31, 2026

Copy link
Copy Markdown
Collaborator

Green:
Seems okay, though I need more context of felonies and the like to fully judge.

Blue:
HOS being required to remain in security on blue alert is strange.

Red:
On Red, requiring HOS to be in security to coordinate is also strange. Often its easier to do that from the bridge, given the consoles there.
Warden does not feel like a tactical field commander. Them going into combat to direct security seems odd.

Suspending SOP on Red is a bit extreme imo. This is kind of a martial law thing in the current paradigm, unless SOP is radically different in the current setup.

Cyan:
There should be more here. What is there currently is not worthy of an alert by itself. It works as a "Kill all silicons except 'so and so borg'". That is not what this is though.


Corporate Espionage Act: I have no idea what this is supposed to be about. Is this meant to be some gradated metashield?


Departmental SOP stuff: Too little to comment on.


Corporate Disciplinary Actions: Hesitant to give IAAs such a wide range of punitive actions.

The punitive actions taken are at the sole discretion of the relevant Head of Staff."

If this is meant to mean that it's just a recommendation, I would highly recommend making them a generic type of warning/demerit/writeup, and say IAAs can recommend them in a seperate section for IAAs. Putting it in the IAA category makes it feel like an IAA power to inflict.


Infractions:

Sec being able to fine people is good. Would need fine guidelines for common value windows.


Docking:
Who can approve docking? It would be good if docking locations had numbers or something assigned to them, and they were visible on the shuttle window. Currently, communicating docks can be rather difficult, without map metaknowledge.


Trading:
Vague


Treatment of Visitors:

Would be better to re-frame visitor regulations to require more generally they stay in public areas, and away from valuable or confidential stuff. There are other valuable things on station than just the research complex.

What is the difference between a visitor and a refugee


Hiring Process:

References non-official paperwork, as "standard".


Order of Succession:
Strange to pick HOS at last resort for temporary leadership. Unsure why it's like that.

Central Command VIPs can call a vote of no confidence should they believe the captain is unable to perform their duties. This can only be called by a vote with a majority of Central Command VIP’s approval.

Nah, they should have to fax for permission to do it. And/or command itself should do it. This will make command players think the CCVIP has control over the capitainship. CMO having the only permission to do it from Command side is weird.


Martial Law:
We have gamma alert for a reason. That is already a very good signifier of martial law. There's no reason to eliminate that aspect. We've just about trained players to associate Gamma with martial law. It is a bit strange feeling to me to define martial law as a question of no viable captain.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants